build: optimize for build size - #7
Merged
Merged
Conversation
svenne87
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Only changes Cargo release build settings; no application logic, auth, or data handling is affected.
Overview
Adds a
[profile.release]block toCargo.tomlso release builds of thecdylibcrate are tuned for smaller artifact size instead of maximum speed.Release builds now use
opt-level = "z"(size-oriented optimization), link-time optimization (lto = true), symbol stripping (strip = true), andcodegen-units = 1to allow more aggressive whole-crate optimization at the cost of longer compile times.Reviewed by Cursor Bugbot for commit b6ccc0a. Bugbot is set up for automated code reviews on this repo. Configure here.